Hi G2 community! I am researching Commenting Systems specifically for integration quality across publishing platforms: a WordPress plugin that works out of the box, a Drupal module that requires custom development, and a JavaScript SDK that takes weeks to embed correctly in a custom CMS.
For development teams that have integrated a commenting system into both WordPress and a custom CMS, which integration was harder than expected, and what was the specific technical step that created the most friction?
##### Post Metadata - Posted at: 4 months ago - Author title: Marketing Executive - Net upvotes: 1 ## Comments ### Comment 1 Full disclosure: I work on GraphComment, so read this as a vendor's view — but the question is about integration mechanics specifically, and there's a distinction the list above skips that actually decides how hard this gets. The five systems here fall into two integration models, and the split matters more than any feature list. Native WordPress plugins (IntenseDebate, Thrive Comments) are one-click, but WordPress-only — Drupal and a custom CMS are out of scope. Universal JS embeds (Disqus, FastComments, Viafoura — and GraphComment) are one snippet that works anywhere, but the "one snippet" claim hides very different amounts of work. Within the embed group, the real friction point is exactly what Mahima flagged about Viafoura: identity. Some embeds require you to wire the comment system into your own auth stack (Auth0 or equivalent) before authenticated commenting works — on a custom CMS that's the multi-week step, not the embed. Others bring their own identity layer, so the snippet really is the whole integration. GraphComment sits in that second camp: a native WordPress plugin (and on WordPress, v5 writes comments back into the native wp_comments table, so you keep the same data safety net people value in IntenseDebate and Disqus), and for Drupal or a custom platform, the same universal embed with its own authentication — no identity system to build first. EU-hosted, no third-party ad tracking. So to answer the original question directly: in a cross-platform rollout the hardest step is almost never the embed — it's identity/auth on the non-WordPress side, and reconciling comment data between your platform's DB and the vendor. An embed that owns its identity layer removes the first friction; one that syncs and exports cleanly removes the second. ##### Comment Metadata - Posted at: 2 months ago - Author title: CEO & Founder @GraphComment - Discussion reinvented ### Comment 2 <p>The detail that stands out is Viafoura being the only one where the evidence calls out a real auth integration requirement, needing Auth0 or an equivalent identity system, while IntenseDebate, Thrive Comments, and Disqus don't mention that dependency at all. That's usually the step that turns a "simple embed" into a multi-week project on a custom CMS. For teams that have actually built one of these out, was identity/auth integration the hidden cost, or did something else in the embed process end up being the bigger time sink?</p> ##### Comment Metadata - Posted at: 3 months ago - Author title: SEO Content Writer #### Reply 1 It's useful for collecting customer feedback, employee opinions, market research, or event responses, and the built-in reporting tools make it simple to turn responses into actionable insights. https://fnf-2.io ##### Reply Metadata - Posted at: 3 months ago - Author title: fnf ## Related discussions - [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team) - Posted at: over 13 years ago - Comments: 6 - [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section) - Posted at: over 13 years ago - Comments: 0 - [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm) - Posted at: over 13 years ago - Comments: 4